5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

RETURN


The RETURN statement transfers execution to the statement following the most recent GOSUB statement.

    ????? RETURN   ??? ?????????????????????? ???
    (1)            (2) (3)                    (4)

(1) T/F execution conditions
(2) Optional application ID
(3) Optional logic field name, logic PDF, or constant
(4) Optional occurrence (constant/index)

Restores True/False Status Indicators

When you invoke a subroutine using the keyword GOSUB, APPX temporarily stores the true/false status indicators and then clears them so that all five indicators are available for use within the subroutine. When RETURN transfers control back to the statement following the GOSUB, the system restores the indicators to the values that existed at the time the GOSUB was invoked. In addition, when implemented, GOSUB will set the next status indicator to the value indicated by the logic field or constant in the RETURN statement, if any.

Execution Errors

If a RETURN is encountered with no previous GOSUB, a non-recoverable error occurs at runtime.

Related Statements

GOSUB

Example

In this example, the same routine is used to post to both the adjustment account and the receivable account. The actual code is copied into the event point from a subroutine process. 

          *        post adjustment
          GOSUB    :POST MTDPOST RECORD
          *        post receivable
          COMPUTE  TAR MTDPOST AMOUNT             *      -1
          SET      TAR MTDPOST ACOUNT             =  TAR ADJUST2 RECEIV ACCOUNT
          GOSUB    :POST MTDPOST RECORD
          *
          END
          *
          LABEL    :POST MTDPOST RECORD
          COPY     TAR POST MTDPOST RECORD
          RETURN

Application Design Manual                                         "Powered by Appx Software"

685

©2006 By APPX Software, Inc. All Rights Reserved